SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Goal modeling</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Goal modeling</span></span>

</h1>

</header>

<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p>A <b>goal model</b> is an element of <a href="Requirements_engineering" title="Requirements engineering">requirements engineering</a> that may also be used more widely in <a href="Business_analysis" title="Business analysis">business analysis</a>. Related elements include <a href="Stakeholder_analysis" title="Stakeholder analysis">stakeholder analysis</a>, <a href="Context_analysis" title="Context analysis">context analysis</a>, and <a href="Scenario_(computing)" title="Scenario (computing)">scenarios</a>,<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> among other business and technical areas.

</p>

<div class="mw-heading mw-heading2"><h2 id="Principles">Principles</h2></div>

<p>Goals are objectives which a system should achieve through cooperation of actors in the intended software and in the environment.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> Goal modeling is especially useful in the early phases of a project. Projects may consider how the intended system meets organizational goals (see also <sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>), why the system is needed and how the stakeholders’ interests may be addressed.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p><p>A goal model:

</p>

<ul><li>Expresses the relationships between a system and its environment (i.e. not only on what the system is supposed to do, but why). The understanding this gives, of the reasons why a system is needed, in its context, is useful because "systems are increasingly used to fundamentally change business processes rather than to automate long-established practices".<sup id="cite_ref-ericyu_5-0" class="reference"><a href="#cite_note-ericyu-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup></li>

<li>Clarifies requirements : Specifying goals leads to asking "why", "how" and "how else".<sup id="cite_ref-ericyu_5-1" class="reference"><a href="#cite_note-ericyu-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> Stakeholders' requirements are often revealed in this process, with less risk of either missing requirements, or of over-specifying (asking for things that are not needed).</li>

<li>Allows large goals to be analyzed into small, realizable goals:</li>

<li>Deals with conflicts : goal modeling can identify and help to resolve tradeoffs between cost, performance, flexibility, security and other goals. It can reveal divergent interests between stakeholders. It can identify conflicts because meeting one goal can interfere with meeting other goals.<sup id="cite_ref-ericyu_5-2" class="reference"><a href="#cite_note-ericyu-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup></li>

<li>Enables requirement completeness to be measured: requirements can be considered complete if they fulfil all the goals in the goal model.</li>

<li>Connects requirements to design: for example, the i* "Non-Functional Requirements (NFR) framework" uses goals to guide the design process.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notations">Notations</h2></div>

<p>There are several notations in use for goal models in software development, including:

</p>

<ul><li><a href="I*" title="I*">i*</a> (pronounced "eye-star") and a variant, <a href="Goal-oriented_Requirements_Language" title="Goal-oriented Requirements Language">GRL</a><sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup></li>

<li><a href="Unified_Modeling_Language" title="Unified Modeling Language">UML</a> <a href="Use_Case" class="mw-redirect" title="Use Case">Use Case</a> diagram<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup></li></ul>

<p>Other notations have been proposed by researchers,<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> while the Goal Structuring Notation (GSN) and GRL are sometimes used to make <a href="Safety_case" title="Safety case">safety cases</a> to satisfy the regulator in safety-related industries.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Goal_modeling_in_i*">Goal modeling in i*</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="I*" title="I*">i*</a></div>

<p>The i* goal modeling notation provides two kinds of diagram:<sup id="cite_ref-i*_13-0" class="reference"><a href="#cite_note-i*-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li>"Strategic Dependency" (SD), defining relationships between roles in terms of specific goals that one role depends on the other role to provide.</li>

<li>"Strategic Rationale" (SR), analyzing the goals identified on the SD model into subsidiary goals and tasks.</li></ul>

<p>i* shows each role (an actor, agent or position) as a large circle containing the goals, tasks, and resources which that role owns. Ownership in i* means that the role desires the satisfaction of its goals, either for its own benefit or for the benefit of some other role. Goals may be accompanied by "obstacles" (negative goals) to be surmounted. Non-functional goals can be modeled as "soft goals" in i*: they are diagrammed as clouds or indented ovals.

</p>

<div class="mw-heading mw-heading3"><h3 id="Goal_modeling_in_KAOS">Goal modeling in KAOS</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="KAOS_(software_development)" title="KAOS (software development)">KAOS (software development)</a></div>

<p>The KAOS goal modeling notation provides a way of defining goals and obstacles, underpinned by a formal (mathematical) method of analysis.<sup id="cite_ref-AvL_2009_8-1" class="reference"><a href="#cite_note-AvL_2009-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Goal_modeling_in_UML">Goal modeling in UML</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Use_case_diagram" title="Use case diagram">Use case diagram</a></div>

<p>UML's <a href="Use_case_diagram" title="Use case diagram">use case diagram</a> provides a simple goal modeling notation. The bubbles name functional goals,<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> so a Use case diagram forms a simple functions-only goal model: as Cockburn writes, use cases cover only the behavioral requirements.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup> Roles are shown as actors (stickmen on the diagram), linked to the use cases in which they take part. The use cases are drawn as elliptical bubbles, representing desired behavioral goals.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup>

</p><p>With the addition of <a href="Misuse_case" title="Misuse case">misuse cases</a>, the notation can model both desired goals and active threats. The misuse case notation shows negative (possibly hostile) stakeholders as the primary actors for the misuse cases; these may be grouped on the right-hand side of the diagram. The notation may assist in discovering suitable mitigating or preventative goals, shown as subsidiary use cases. These often have the aim of improving security, safety, or reliability, which are non-functional goals. <a href="Non-functional_requirement" title="Non-functional requirement">Non-functional requirements</a> can to some extent be described in use case style using misuse cases to define negative goals; but the (positive) goals thus discovered are often functional. For example, if theft is a threat to <a href="Security" title="Security">security</a>, then fitting locks is a mitigation; but that a door can be locked is a functional requirement.<sup id="cite_ref-MisuseCase_17-0" class="reference"><a href="#cite_note-MisuseCase-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup>

</p><p>The counterpoint is that Use Cases are not from Cognitive Science roots, whereas i* and KAOS are. Indeed, the literature behind Use Cases does not include discussion Goal Intention, Goal Refinement, Ends-Means, does not call out Rasmussen et cetera. There may be a predilection to relate Use Cases to Goals because of the visual metaphor of Goals rather than the semantics of Goal Refinement per Cognitive Science.

</p>

<div class="mw-heading mw-heading2"><h2 id="Bibliography">Bibliography</h2></div>

<ul><li>Alexander, Ian and Beus-Dukic, Ljerka. <i>Discovering Requirements: How to Specify Products and Services</i>. Wiley, 2009.</li>

<li>Alexander, Ian F. and Maiden, Neil. <i>Scenarios, Stories, Use Cases</i>. Wiley, 2004.</li>

<li><a href="Cockburn%2C_Alistair" class="mw-redirect" title="Cockburn, Alistair">Cockburn, Alistair</a>. <i>Writing Effective Use Cases</i>. Addison-Wesley, 2001.</li>

<li><a href="Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Fowler, Martin</a>. <i>UML Distilled</i>. 3rd Edition. Addison-Wesley, 2004.</li>

<li><a href="Axel_van_Lamsweerde" title="Axel van Lamsweerde">van Lamsweerde, Axel</a>. <i>Requirements Engineering: from system goals to UML models to software specifications</i>. Wiley, 2009.</li>

<li>Yu, Eric, Paolo Giorgini, Neil Maiden and <a href="John_Mylopoulos" title="John Mylopoulos">John Mylopoulos</a>. (editors) <i>Social Modeling for Requirements Engineering</i>. MIT Press, 2011.</li></ul>

<ul><li><a href="Benefit_dependency_network" title="Benefit dependency network">Benefit dependency network</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 33em;">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text">Alexander and Beus-Dukic, 2009. Pages 17-18</span>

</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFLin_Liu_and_Eric_Yu2003" class="citation web cs1">Lin Liu and Eric Yu (2003). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20050205073259/http://www.cs.toronto.edu/~liu/publications/ISj03.pdf">"Designing information systems in social context: a goal and scenario modelling approach"</a> <span class="cs1-format">(PDF)</span>. University of Toronto. Archived from <a rel="nofollow" class="external text" href="http://www.cs.toronto.edu/~liu/publications/ISj03.pdf">the original</a> <span class="cs1-format">(PDF)</span> on February 5, 2005.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite id="CITEREFEllis-BraithwaiteLock,_R.Dawson,_R.Haque_B.2013" class="citation journal cs1">Ellis-Braithwaite, R.; Lock, R.; Dawson, R.; Haque B. (2013). "Towards an Approach for Analysing the Strategic Alignment of Software Requirements using Quantified Goal Graphs". <i>International Journal on Advances in Software</i>. <b>6</b>: <span class="nowrap">119–</span>130. <a href="ArXiv_(identifier)" class="mw-redirect" title="ArXiv (identifier)">arXiv</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://arxiv.org/abs/1307.2580">1307.2580</a></span>. <a href="Bibcode_(identifier)" class="mw-redirect" title="Bibcode (identifier)">Bibcode</a>:<a rel="nofollow" class="external text" href="https://ui.adsabs.harvard.edu/abs/2013arXiv1307.2580E">2013arXiv1307.2580E</a>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">E. Yu, "Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering", 1997 IEEE</span>

</li>

<li id="cite_note-ericyu-5"><span class="mw-cite-backlink">^ <a href="#cite_ref-ericyu_5-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-ericyu_5-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-ericyu_5-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFEric_Yu_and_John_Mylopoulos" class="citation web cs1">Eric Yu and John Mylopoulos. <a rel="nofollow" class="external text" href="http://www.cs.toronto.edu/pub/eric/REFSQ98.html">"Why Goal-Oriented Requirements Engineering"</a>. University of Toronto.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text">K.Pohl and P. Haumer, "Modelling Contextual Information about Scenarios", Proc. 3rd Int. Workshop on Requirements Engineering: Foundations of Software Quality REFSQ ’97, Barcelona, Catalonia, Spain, June 1997 pp. 187-204.</span>

</li>

</li>

<li id="cite_note-AvL_2009-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-AvL_2009_8-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-AvL_2009_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><a href="Axel_van_Lamsweerde" title="Axel van Lamsweerde">van Lamsweerde</a>, 2009.</span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text">Fowler, 2004. Pages 99-105</span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite id="CITEREFRolland,_ColettePrakash,_NaveenBenjamen,_Adolphe1999" class="citation journal cs1"><a href="Colette_Rolland" title="Colette Rolland">Rolland, Colette</a>; Prakash, Naveen; Benjamen, Adolphe (1999). <a rel="nofollow" class="external text" href="http://hal.archives-ouvertes.fr/docs/00/70/75/68/PDF/A_multi_model_view_REJ.pdf">"A Multi-Model View of Process Modelling"</a> <span class="cs1-format">(PDF)</span>. <i>Requirements Engineering</i>. <b>4</b> (4): <span class="nowrap">169–</span>187. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1007%2Fs007660050018">10.1007/s007660050018</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:6988662">6988662</a>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.goalstructuringnotation.info">GSN Community Standard</a></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite id="CITEREFFeodoroff2016" class="citation book cs1">Feodoroff, R. (2016). "Intentional enterprise architecture". <i>2016 Annual IEEE Systems Conference (SysCon)</i>. pp. <span class="nowrap">1–</span>8. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FSYSCON.2016.7490555">10.1109/SYSCON.2016.7490555</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4673-9519-9</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:206586399">206586399</a>.</cite></span>

</li>

<li id="cite_note-i*-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-i*_13-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFYu,_Eric2011" class="citation web cs1">Yu, Eric (September 6, 2011). <a rel="nofollow" class="external text" href="http://www.cs.toronto.edu/km/istar/">"i*"</a>. <i>i*: an agent- and goal-oriented modelling framework</i>. University of Toronto<span class="reference-accessdate">. Retrieved <span class="nowrap">December 17,</span> 2011</span>.</cite></span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text">Alexander and Beus-Dukic, 2009. Page 121</span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text">Cockburn, 2001. Page 62</span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text">Cockburn, 2001. Page 221</span>

</li>

<li id="cite_note-MisuseCase-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-MisuseCase_17-0">^</a></b></span> <span class="reference-text">Alexander and Maiden, 2004. Chapter 7. Pages 119-139.</span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="http://www.cs.toronto.edu/km/istar/">i* Official Website, with tutorial and bibliography</a> - "an agent- and goal-oriented modelling framework"</li>

<li><a rel="nofollow" class="external text" href="https://sites.google.com/site/istarlanguage/home">i* wiki with guidelines and examples</a></li>

<li><a rel="nofollow" class="external text" href="http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf">KAOS tutorial</a></li>

<li><a rel="nofollow" class="external text" href="http://ceur-ws.org/Vol-337/paper9.pdf">Using EEML for Combined Goal and Process Oriented Modeling: A Case Study</a> - John Krogstie</li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2023-09-04" href="https://en.wikipedia.org/wiki/?title=Goal_modeling&oldid=1173846253">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>